Reviews the REA model method for designing AIS. What is an REA model?
An REA model is a framework to design accounting systems that can be integrated with other enterprise data, which helps control and plan every aspect of a company’s business processes.
How is the REA model of benefit to AIS designers and developers?
REA modeling helps database designers define a complete set of entities and attributes.
Entities: can be classified as a resource, event, agent, or location about which data are collected. Is represented as a table. It is anything in which we are interested that exists independently
Attributes: are items of data that characterize an entity or relationship. Attributes that consist of multiple subattributes are called composite attributes. A key attribute is the attribute whose value is unique for every enitity that will appear in the database and is the most meaningful way of identifying each entity. The key attribute becomes the primary key.
Relationships: are associations between entities. The entities must be logically linked to represent the relationships that exist between them. The mapping of the relationships between entities provides a roadmap for getting from one piece of data in the database to another related piece of data.
Types of Relationships:
Types of relationships that occur: 1:N, M:N, and 1:1
Relationship types in REA model of client billing business process:
-Relationship for expanding attribute description – involves examining prescribed entities in pairs to identify logical linkages that would improve the description of an entity’s attributes
-Recursive relationship – a relationship between two different instances of an entity
Mapping the REA model to a Relational Database (discuss the steps):
1. Create a separate table for each entity
2. Determine the primary key for each of the relations. Primary key must uniquely identify the row.
3. Determine the attributes for each of the entities.
4. Implement the relationships among entities making sure the primary key in one table also exists as an attribute in every table where there is a relationship.
Types of relationships
1:N or N:1 one to many or many to one
1:1 one to one
M:N many to many
5. Determine the attributes for each of the relationship tables.
REA Model:
Reviews the REA model method for designing AIS.What is an REA model?
An REA model is a framework to design accounting systems that can be integrated with other enterprise data, which helps control and plan every aspect of a company’s business processes.
How is the REA model of benefit to AIS designers and developers?
REA modeling helps database designers define a complete set of entities and attributes.
- Entities: can be classified as a resource, event, agent, or location about which data are collected. Is represented as a table. It is anything in which we are interested that exists independently
- Attributes: are items of data that characterize an entity or relationship. Attributes that consist of multiple subattributes are called composite attributes. A key attribute is the attribute whose value is unique for every enitity that will appear in the database and is the most meaningful way of identifying each entity. The key attribute becomes the primary key.
- Relationships: are associations between entities. The entities must be logically linked to represent the relationships that exist between them. The mapping of the relationships between entities provides a roadmap for getting from one piece of data in the database to another related piece of data.
- Types of Relationships:
Types of relationships that occur: 1:N, M:N, and 1:1Relationship types in REA model of client billing business process:
-Relationship for expanding attribute description – involves examining prescribed entities in pairs to identify logical linkages that would improve the description of an entity’s attributes
-Recursive relationship – a relationship between two different instances of an entity
Mapping the REA model to a Relational Database (discuss the steps):
1. Create a separate table for each entity2. Determine the primary key for each of the relations. Primary key must uniquely identify the row.
3. Determine the attributes for each of the entities.
4. Implement the relationships among entities making sure the primary key in one table also exists as an attribute in every table where there is a relationship.
Types of relationships
1:N or N:1 one to many or many to one
1:1 one to one
M:N many to many
5. Determine the attributes for each of the relationship tables.